X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C83D04.484F2E21@onstor-exch02.onstor.net>; Wed, 12 Dec 2007 13:16:38 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C83D04.484F2E21"
Content-class: urn:content-classes:message
Subject: RE: Directory and file name cleanup (ex. agile)
Date: Wed, 12 Dec 2007 13:16:38 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05C73DD7@onstor-exch02.onstor.net>
In-Reply-To: <20071212130803.1f3558ea@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Directory and file name cleanup (ex. agile)
Thread-Index: Acg9AxVhq9uNBGoHTpOwC7goI0MZpQAAD9SA
From: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	<dl-designreview>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C83D04.484F2E21
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, December 12, 2007 1:08 PM
To: dl-designreview
Subject: Directory and file name cleanup (ex. agile)

=20

I have prepared a changelist that cleans up the use of the word 'agile'

in file and directory names, and also removes /usr/local/agile from our

software.  Here are the details:

=20

1. /usr/local/agile as a directory has not existed now for several

releases, so it's time to eradicate it.  Change all references to that

directory to /onstor where the files really live.

=20

2. agile.conf is a dead file, remove references to it and remove it

from the build.

=20

3. /var/agile will be split into two different directories: /var/onstor

for trace files and core dumps (although there is some claim core dumps

go in /var/run anyway);=20

[Sandrine] yes, all deamons cores go to /var/run (except nfxsh, which
cores wherever it's run from)

=20

and /var/log/onstor for log files, including the

elog messages file, which will now be /var/log/onstor/messages.  This is

because /var/agile had become an arbitrary dumping ground without any

paradigm or logically intuitive organization.

[Sandrine] where would the bsd|linux syslog messages go? Right now we
have /var/agile/messages* for elogs and /var/log/messages* for bsd
syslog

=20

=20

Scope:

=20

All work necessary to complete this should already be done and viewable

in the changelist 26643.  There should be no extra changes necessary by

anyone else, except of course documentation changes.  If you see

something is missing, please inform me.

=20

Timeline:

=20

This will go into the release following R98 as well as Cougar, so

the soonest it will hit customers is in about 3.5 months.  The idea is

to get some general use testing of the change in Development, QA and

Support to fine tune any rough spots prior to release.  In addition the

3 months should and provide plenty of acclimation time.

=20

Data points:

=20

Upgrading.  This may require that we obsolete the previous upgrade

method (system upgrade), and all upgrades for S-W use the upgrade

script.

=20

Implications for data warehouse?  Should be none, but ....


------_=_NextPart_001_01C83D04.484F2E21
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 77.95pt 1.0in 77.95pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dnavy>

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>-----Original Message-----<br>
From: Andy Sharp <br>
Sent: Wednesday, December 12, 2007 1:08 PM<br>
To: dl-designreview<br>
Subject: Directory and file name cleanup (ex. agile)</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>I have prepared a changelist that cleans up the use of the word =
'agile'<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>in file and directory names, and also removes /usr/local/agile =
from our<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>software.&nbsp; Here are the =
details:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>1. /usr/local/agile as a directory has not existed now for =
several<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>releases, so it's time to eradicate it.&nbsp; Change all =
references to
that<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>directory to /onstor where the files really =
live.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>2. agile.conf is a dead file, remove references to it and remove =
it<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>from the build.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>3. /var/agile will be split into two different directories: =
/var/onstor<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>for trace files and core dumps (although there is some claim =
core dumps<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>go in /var/run anyway); <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblue face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:blue'>[Sandrine] yes, all deamons cores =
go to /var/run
(except nfxsh, which cores wherever it's run =
from)<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>and /var/log/onstor for log files, including =
the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>elog messages file, which will now be =
/var/log/onstor/messages.&nbsp;
This is<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>because /var/agile had become an arbitrary dumping ground =
without any<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>paradigm or logically intuitive =
organization.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblue face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;color:blue'>[Sandrine] where would the =
bsd|linux syslog
messages go? Right now we have /var/agile/messages* for elogs and
/var/log/messages* for bsd syslog<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Scope:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>All work necessary to complete this should already be done and =
viewable<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>in the changelist 26643.&nbsp; There should be no extra changes
necessary by<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>anyone else, except of course documentation changes.&nbsp; If =
you see<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>something is missing, please inform =
me.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Timeline:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>This will go into the release following R98 as well as Cougar, =
so<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>the soonest it will hit customers is in about 3.5 months.&nbsp; =
The
idea is<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>to get some general use testing of the change in Development, QA =
and<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Support to fine tune any rough spots prior to release.&nbsp; In
addition the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>3 months should and provide plenty of acclimation =
time.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Data points:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Upgrading.&nbsp; This may require that we obsolete the previous =
upgrade<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>method (system upgrade), and all upgrades for S-W use the =
upgrade<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>script.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Implications for data warehouse?&nbsp; Should be none, but =
....<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C83D04.484F2E21--
